Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

branch-3.0: [fix](cloud) fix BlockFileCache::get_or_set crash #44013 #44146

Merged
merged 1 commit into from
Nov 20, 2024

Conversation

github-actions[bot]
Copy link
Contributor

Cherry-picked from #44013

This is a Plan-B fix, the root cause is under study:

2# JVM_handle_linux_signal in
/usr/lib/jvm/java-17-openjdk-amd64/lib/server/libjvm.so
 3# 0x00007F8CFE720520 in /lib/x86_64-linux-gnu/libc.so.6
4# std::_Rb_tree_decrement(std::_Rb_tree_node_base*) at
../../../../../libstdc++-v3/src/c++98/tree.cc:123
5#
doris::io::BlockFileCache::get_impl[abi:cxx11](doris::io::UInt128Wrapper
const&, doris::io::CacheContext const&, doris::io::FileBlock::Range
const&, std::lock_guard<std::mutex>&) at
/home/zcp/repo_center/doris_branch-3.0/doris/be/src/io/cache/block_file_cache.cpp:365
6# doris::io::BlockFileCache::get_or_set(doris::io::UInt128Wrapper
const&, unsigned long, unsigned long, doris::io::CacheContext&) at
/home/zcp/repo_center/doris_branch-3.0/doris/be/src/io/cache/block_file_cache.cpp:662
7# doris::io::CachedRemoteFileReader::read_at_impl(unsigned long,
doris::Slice, unsigned long*, doris::io::IOContext const*) at
/home/zcp/repo_center/doris_branch-3.0/doris/be/src/io/cache/cached_remote_file_reader.cpp:179


Signed-off-by: zhengyu <[email protected]>
@doris-robot
Copy link

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@dataroaring dataroaring reopened this Nov 18, 2024
@doris-robot
Copy link

run buildall

Copy link
Contributor Author

clang-tidy review says "All clean, LGTM! 👍"

@dataroaring dataroaring merged commit 0b98983 into branch-3.0 Nov 20, 2024
21 of 23 checks passed
@github-actions github-actions bot deleted the auto-pick-44013-branch-3.0 branch November 20, 2024 01:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants